PUBLIC MARKS from Monique with tags [en] & accessibilité

At the moment there’s no real kudos for agencies that meet accessibility requirements. No recognition for complying, public mention of best practice examples or awards for high achievement.

I’m not a huge fan of skip links as a solution for screen reader users on desktop but agree wholeheartedly that visible ones are extremely helpful for sighted keyboard only users who, unlike screen reader users, are forced to tab through content in a linear fashion.

The aim of this article is to inform the reader about accessible services and how to gain access to them. Because some services require specific hardware for their access, we will provide limited descriptions of hardware.

I do not have all the answers and I would love to hear from anyone who can contribute to these ideas.

When creating transcripts for videos, adding details about the setting, actions and such may be beneficial to those relying solely on the transcript. Once the spoken word is captured, that text can be used to caption the video (again, essential for accessibility) and repurposed to create products in other formats. Definitely a win-win scenario!

Without having specialized technical knowledge tied to accessibility, do managers have the skills required to assess if their sites are accessible?

The 2010 WebAIM Screen Reader Survey found that only 1.6% of screenreader users have no Javascript when browsing (compared to 10.4% the previous year) so that argument is wearing thin.

The most common mistakes made in web accessibility have more to do with a failure to understand what constitutes accessible content than with a failure to understand the technology.

What the arguments attempt to assert is, essentially, that “Checklist” accessibility is not good enough, either because the checklists themselves are flawed or that the checklist takes the disabled user out of the equation and relegates their challenges to the level of a series of check items.

Follow some of these ideas in the future of your layouts. You may be surprised at how positive interactions can be when web processes are slowed and streamlined for efficiency. Regardless of browsers or software you can implement these great changes into your site affecting all bouts of incoming traffic.

This paper looks at some technologies and concepts used by people with disabilities, and how these technologies and ideas have grown from, or with assistive technology.

The presentation considered how many people over the age of 60 use the web, how much they use it and why they use it. It outlined some common issues older web users encounter and the general lack of awareness by them about how they can control the presentation of web content.

Images make web pages interesting. So let’s make them useful for everyone, not just those that can see them.

some tips to get you started when setting up a screen reader testing environment.

What’s less commonly known is that there are five different classes of image used on web pages and each of those images requires a different approach to writing the ‘alt’ attribute.

Recordings of screen readers using widgets with and without WAI-ARIA can be a good educational resource for why ARIA is important to accessibility. There aren’t many out there, but here’s what I found.

The same image may require a different text alternative when it plays a different role or is used in a different context.

The Ubuntu Accessibility Team is a joint community and Canonical team which works on development, testing, support, and documentation for accessibility for people with sensory, cognative, physical, and any other type of impairments.

Worldspace FireEyes is an unprecedented, nextgen web accessibility tool that ensures both static and dynamic content within a web portfolio are compliant with standards such as Section 508, WCAG 1.0, and WCAG 2.0.